Received: from unknown (HELO nexus.space.net.au) (203.38.10.2) by pop.onelist.com with SMTP; 5 Sep 1998 00:23:42 -0000
Received: from default (per1-42.space.net.au [203.38.10.212]) by nexus.space.net.au (8.9.1/8.8.7) with SMTP id IAA03604 for <amos-list@onelist.com>; Sat, 5 Sep 1998 08:19:50 +0800
Message-ID: <35EF3233.64E1@ozemail.com.au>
Date: Fri, 04 Sep 1998 08:20:03 +0800
From: Andy H <geosync@ozemail.com.au>
X-Mailer: Mozilla 3.04 (Win95; I)
To: Amos List <amos-list@onelist.com>
Mailing-List: list amos-list@onelist.com; contact http://www.onelist.com
Delivered-To: mailing list amos-list@onelist.com
Precedence: bulk
Reply-to: amos-list@onelist.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [amos-list] LHA Trashing
Status: O
X-Status:
From: Andy H <geosync@ozemail.com.au>
Hi all,
On the subject of LHA's being corrupted, I have found that some servers
don`t recognize the LHA suffix and treat it as some sort of unspecific
binary file (ergo goodbye LHA). The easiest way to stop this from
happening is to archive as usual using LHA but rename it to #?.ZIP when
sending it over the Internet. Most servers respect the archive
structure of the IBM ZIP file and wont tamper with it. When the user
recieves the "fake" ZIP file they can simply rename it and unpack with